Check category: Availability

Check description: Checks if any Cluster Server(VCS) agents have faulted and are not running.

Check procedure:

• Retrieves the state of the agents on the target system nodes.

Check recommendation: The system does not monitor cluster Server(VCS) resources that belong to a type whose agent has faulted are not monitored. To restart the agent-:
1. Login as root
2. Start the agent-
    # haagent -start Agent -sys node
2. Confirm that the agent has restarted-
    # haagent -display Agent

Learn More...

Check category: Availability

Check description: Checks if any faulted VCS resource of each configured VCS group.

Check procedure:

• Fetches the resources from all the systems specified for executing the check.

Check recommendation: A group cannot failover to a system where the Cluster Server (VCS) resource has faulted. Fix the problem that caused the fault. To clear the VCS fault for resource resource_name on node node_name login as root enter:
#hares -clear resource_name node_namei.
If a parallel service group like Cluster Volume Manager(CVM) or Cluster File System (CFS) fails,clear the VCS fault for the service group and bring the service group online. Log in as root and enter:
#hagrp -clear service_group_name -sys node_name.
#hagrp -online service_group_name -sys node_name

Learn More...

Check category: Availability

Check description: Checks whether the application binaries exist and are executable.

Check procedure:

• Fetches the list of application binaries specified for monitoring in the configuration on the target cluster systems.

Check recommendation: Make sure that the scripts specified in the cluster configuration exist and that they are executable on all the systems in the cluster.

Learn More...

Check category: Availability

Check description: Checks if at least one VCS resource of each configured VCS group is marked as critical.

Check procedure:

• Retrieves the details of all the resources of the configured groups.

Check recommendation: A group cannot failover to an alternate system unless it has at least one resource marked as critical. Therefore, to ensure maximum high availability, as root execute the following command to set affected resources to critical: hares -modify resource_name Critical 1.

Learn More...

Check category: Availability

Check description: Checks whether duplicate disk groups are configured on the specified nodes.

Check procedure:

• Fetches the disk group names configured for the cluster systems.

Check recommendation: To facilitate a successful failover, make sure that there is only one disk group name configured for the specified node. To list the disk groups on a system, enter the following command:
# vxdg list.

Learn More...

Check category: Availability

Check description: Checks if minimum two links configured as LLT links.

Check procedure:

• Identifies all the LLT links configured on the system.

Check recommendation: To ensure HA, It is mandatory that you should have the minimum two links configured as LLT links.

Learn More...

Check category: Availability

Check description: Checks for the availability of LLT high-priority links and verifies if they are in the private network.

Check procedure:

• Verifies whether the LLT Links are configured on a private link and as high priority by using the lltstat command.

Check recommendation: It is recommended that you have at least two high-priority LLT links which are required to configure LLT in the private network.

Learn More...

Check category: Availability

Check description: Checks whether any VCS resource has been disabled.

Check procedure:

• Executes hares -display command.

Check recommendation: Enable the VCS resource. As root do:
# haconf -makerw
# hares -modify resource_name Enabled 1
# haconf -dump -makero.

Learn More...

Check category: Availability

Check description: Checks for consistency of license files across cluster nodes.

Check procedure:

• Identifies the license keys, license key types and license key versions installed on all the nodes in a cluster.

Check recommendation: Ensures that license keys, license key types and license key versions installed on all the nodes in a cluster are consistent. Inconsistent license keys, license key types and license key versions installed can cause errors in application fail-over.

Learn More...

Check category: Availability

Check description: Checks for consistency of Trigger directory and Trigger files across cluster nodes.

Check procedure:

• Identifies VCS Triggers directory and files on the active node.

Check recommendation: Ensures that the same trigger files and their path exist on all cluster nodes.

Learn More...

Check category: Availability

Check description: Checks whether the input systems in a cluster have the same operating system, operating system version, and operating system patch level. These attributes should be identical on all systems in a VCS cluster.

Check procedure:

• Determines the OS, OS version, and the OS patches installed on the cluster systems.

Check recommendation: Ensure that the input systems in a cluster have the same operating system, operating system version, and operating system patch level.

Learn More...

Check category: Availability

Check description: Checks if any Cluster Server(VCS) MountV resource has the ForceUnmount attribute set to ALL.

Check procedure:

• Retrieves the details of all MountV resources of the configured groups.

Check recommendation: Only enable this option if you are sure that no applications or users are writing to the volume.

Learn More...

Check category: Availability

Check description: Checks whether the checksums of application executables on the target systems match the checksums on the system where the application is online.

Check procedure:

• Fetches the list of applications configured for monitoring on the target cluster systems.

Check recommendation: The checksum of each executable file should be the same on all nodes. Identify the definitive and correct executable file on one of the cluster nodes, then synchronize the files on the remaining failover nodes.

Learn More...

Check category: Availability

Check description: Checks if each cluster discovered in the set of input nodes has a unique name.

Check procedure:

• Fetches the cluster names of all the clusters discovered in the input cluster nodes.

Check recommendation: Cluster names should be unique. If you plan to set up the Global Cluster Option(GCO) between clusters with identical cluster names, change cluster names.

Learn More...

Check category: Availability

Check description: Checks whether all Dynamic Multi-Pathing (DMP) paths to the array are in the active/enabled state.

Check procedure:

• Identifies all the DMP subpaths for all the available disks on the system.

Check recommendation: Enable all the disabled controllers on the system. You can do so using DMP commands.

Learn More...

Check category: Availability

Check description: Checks for Volume Manager disks in the error state.

Check procedure:

• Identify the disks under the control of Volume Manager.

Check recommendation: Inspect the hardware configuration to confirm that the hardware is functional and configured properly.

Learn More...

Check category: Availability

Check description: Check whether all the disks in the VMDg disk group are visible on the cluster node.

Check procedure:

• Fetch all the disk groups configured on the target cluster nodes

Check recommendation: Make sure that all VxVM disks have been discovered.

Learn More...

Check category: Availability

Check description: Check if each cluster discovered in the input nodes set has a unique name.

Check procedure:

• Fetche the cluster names of all the clusters discovered in the input cluster nodes.

Check recommendation: Cluster names should be unique. If you plan to set up the Global Cluster Option(GCO) between clusters with identical cluster names, change cluster names.

Learn More...

Check category: Availability

Check description: Checks if any of the private links in the cluster are in the jeopardy state.

Check procedure:

• Checks the network connectivity of the target host with the other hosts in the cluster.

Check recommendation: 1. Determine the connectivity of this node with the remaining nodes in the cluster -Enter:
%VCS_HOME%\bin\lltstat.exe -nvv. If the status is DOWN this node cannot see that link to the other node(s).
2. Restore connectivity through this private link.
3. Verify that connectivity has been restored -Enter:
%VCS_HOME%\bin\gabconfig.exe -a.If this command does not have 'jeopardy' in the output, the link has been restored.

Learn More...

Check category: Availability

Check description: Checks whether the existing cluster configuration in the %VCS_HOME%\conf\config directory can be used to start VCS on a system.

Check procedure:

• Fetches the VCS configuration in the %VCS_HOME%\conf\config directory on the cluster node.

Check recommendation: Fixes the VCS configuration in the %VCS_HOME%\conf\config directory on the cluster node.

Learn More...

Check category: Configuration

Check description: Checks whether the installed Storage Foundation / InfoScale products have the latest software version.

Check procedure:

• Identifies all the Storage Foundation / InfoScale products and their versions installed on the system.

Check recommendation: It is recommended that you install the latest software level of the Storage Foundation / InfoScale products on the system. This will help you avoid known risks or issues.

Learn More...

Check category: Performance

Check description: Checks for mirrored volumes that do not have a Dirty Region Log (DRL).

Check procedure:

• Identifies any mirrored volumes present on the system.

Check recommendation: The mirrored volume(s) do not have a DRL. Make sure that you create a DRL for any mirrored volumes. A DRL tracks the regions that have changed. Having a DRL helps with data recovery after a system crash. The DRL uses the tracking information to recover only those portions of the volume that need to be recovered. Without a DRL, recovery involves copying the full content of the volume between its mirrors; this process is lengthy and I/O intensive.

Learn More...